Independent readiness determination for automated external defibrillator deployment

ABSTRACT

An apparatus for independent readiness determination for AED deployment includes a controller configured to detect an AED enclosure event corresponding to one or more AEDs registered to be disposed within one or more corresponding AED enclosures, where the controller is configured to communicate data for classifying an AED enclosure event into a predetermined event category, and further includes a communication interface configured to communicate a response action in response to data of the AED enclosure event satisfying one or more predetermined criteria for the predetermined event category. A method and a computer program product also perform the functions of the apparatus.

CROSS-REFERENCES TO RELATED APPLICATIONS

This is a continuation-in-part application of and claims priority toU.S. patent application Ser. No. 16/422,796 entitled “INDEPENDENTREADINESS DETERMINATION FOR AUTOMATED EXTERNAL DEFIBRILLATOR DEPLOYMENT”and filed on May 24, 2019, for Charles L. Malott et al., the entirecontents of which is incorporated herein by reference for all purposeslegally allowed.

FIELD

The subject matter disclosed herein relates to automated externaldefibrillator enclosure devices and more particularly relates toindependent readiness determination for automated external defibrillatordeployment.

BACKGROUND

Sudden Cardiac Arrests (“SCAs) which occur outside of a hospital accountfor hundreds of thousands of deaths annually in the United States alone.Even in cases in which SCA victims survive long enough to be admitted toa hospital, a significant percentage of SCA victims do not survive tohospital discharge, and of those who are discharged many suffer impairedneurological function.

Early defibrillation using an automated external defibrillator (“AED”)is one of the best ways to improve SCA outcomes and save lives. However,installing an AED and hoping that a nearby responder will takeappropriate action quickly enough to save the SCA victim's life fails tomaximize the SCA victim's chances of survival.

Numerous models of AEDs exist which are manufactured by variousmanufacturers and have different features, different recommendations forstoring to ensure that the AED is ready for use, different instructions,different interfaces, and so forth. Even though most AED manufacturersoffer guidance for maintaining these in a ready to use state, someexisting AEDs are stored in a way that fails to ensure that the AEDitself is ready to be successfully used. Additionally, many potentialresponders are unaware of beneficial information that would helpmaximize the likelihood of successfully using an AED to respond to anSCA. Moreover, existing AED readiness recommendations and/or mechanismsfail to adequately address responder readiness.

SUMMARY

An apparatus for independent readiness determination for AED deploymentis disclosed. A method and computer program product also perform thefunctions of the apparatus. One apparatus for independent readinessdetermination for AED deployment includes a controller configured todetect an AED enclosure event corresponding to an AED registered to bedisposed within an AED enclosure, where the controller is configured tocommunicate data for classifying an AED enclosure event into apredetermined event category, and further includes a communicationinterface configured to communicate a response action in response todata of the AED enclosure event satisfying one or more predeterminedcriteria for the predetermined event category, where the communicationinterface is configured to periodically awaken and attempt to establisha wireless network connection for communicating AED enclosure event datausing one or more credentials of a predetermined series of credentialsselected from primary credentials, secondary credentials, and rescuecredentials.

In various embodiments, the controller is configured to collect one ormore AED readiness parameters selected from: an individual enclosureidentifier for linking the AED enclosure to an individual AED identifierof the AED registered to be disposed within the AED enclosure; anenclosure access indicator that indicates whether the AED enclosure isopen; an AED-presence indicator that indicates whether the AED iscorrectly disposed within the AED enclosure; an audible readinessindicator of the AED; a visual readiness indicator of the AED; and astorage environment indicator that measures a temperature, and/or ahumidity within the AED enclosure.

In certain embodiments, the controller is configured to collect the oneor more AED readiness parameters using one or more of: a sensor that isphysically separate from and electrically unconnected to the AED; and auser interface of a mobile communication device. In some embodiments,the individual enclosure identifier is externally coupled to the AEDenclosure and/or internally stored in a tangible memory. In someembodiments, the sensor is disposed inside the AED enclosure.

In various embodiments, the controller is configured to communicate withan access sensor configured to determine whether an access door of theAED enclosure is open. In one embodiment, the apparatus is configured towake the controller from a dormant mode to an active mode in response tothe access sensor determining that the access door is open. In variousembodiments, the controller further communicates with an object sensorconfigured to determine whether the AED is disposed correctly within theAED enclosure. In certain embodiments, the object sensor includes atime-of-flight sensor configured to measure a reflected signal distanceto determine whether the AED is correctly disposed within the AEDenclosure.

In some embodiments, the controller communicates with an inputtransducer configured to collect audio data of the audible readinessindicator. In certain embodiments, the apparatus includes a filter thatdistinguishes the audible readiness indicator from sounds that fail tosatisfy predetermined parameters for the audible readiness indicator. Invarious embodiments, the filter performs frequency domain processing andtime domain processing on the audio data captured by the inputtransducer to distinguish the audible readiness indicator from thesounds that fail to satisfy the predetermined parameters for the audiblereadiness indicator. In one embodiment, the controller is part of acommunication device external to the AED enclosure, where thecommunication device includes all a user interface configured to collectthe one or more AED readiness parameters through the user interface.

A method for independent readiness determination for AED deployment isdisclosed. In one embodiment, the method includes: initiating a requestfor a network connection between a plurality of stationary AED readinessapparatuses and a data network using one or more credentials selectedfrom a predetermined series of credentials selected from primarycredentials, secondary credentials, and rescue credentials forauthenticating the plurality of stationary AED readiness apparatuses tothe data network; and in response to establishing the network connectionbetween the plurality of stationary AED readiness apparatuses and thedata network: communicating event data for an automated externaldefibrillator (“AED”) enclosure event the AED enclosure eventcorresponding to an AED registered to be disposed within an AEDenclosure; classifying the AED enclosure event into a predeterminedevent category; and communicating a response action in response to theAED enclosure event.

In some embodiments, the event data includes user input data collectedthrough a user interface and sensor data collected through one or moresensors that are physically separate from the AED and electricallyunconnected to the AED, the method further comprising: performing acomparison of the user input data and the sensor data; and communicatingresults of the comparison to a mobile communication device, and/or to asecond communication device. In various embodiments, the event dataincludes user input data collected through a user interface the methodfurther including communicating the response action to facilitateconfiguration of the AED enclosure with an updated controller configuredto collect the sensor data from at least one of the one or more sensorsdisposed within the AED enclosure.

In certain embodiments, the predetermined event category for the AEDenclosure event is selected from an emergency response event, amaintenance event, and/or a fault event. In various embodiments,communicating the response action to the mobile communication device isperformed in response to determining that the mobile communicationdevice corresponds to a responder having a readiness status thatsatisfies one or more predetermined criteria for the predetermined eventcategory. In some embodiments, the method further includes determiningthe readiness status of the responder based on a parameter selected froma level of training to respond to the AED enclosure event, a location ofthe mobile communication device corresponding to the responder, a userinput indicating readiness of the responder, and/or an AED eventresponse history of the responder.

A computer program product is disclosed that includes a computer programproduct comprising a non-transitory computer readable storage mediumhaving program instructions embodied therewith, wherein the programinstructions are executable by a mobile communication device to causethe mobile communication device to: configure a predetermined series ofcredentials selected from primary credentials and secondary credentialsfor attempting to connect a plurality of stationary AED readinessapparatuses to a data network; configure a mobile communication deviceas a temporary access point accessible using predetermined rescuecredentials for one or more timed out AED readiness apparatuses tocommunicate one or more updated primary credentials and/or secondarycredentials to the timed out AED readiness apparatuses; and in responseto the AED readiness apparatus connecting to the data network: obtainevent data for an automated external defibrillator (“AED”) enclosureevent detected by a detector controller, the AED enclosure eventcorresponding to an AED registered to be disposed within an AEDenclosure; obtain responder data indicating a readiness status for aresponder that is a user of the mobile communication device; andcommunicate a response action in response to classifying the AEDenclosure event into a predetermined event category and determining thatthe readiness status for the responder satisfies predetermined criteria.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not, therefore, to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of asystem for independent readiness determination for AED deployment;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus for independent readiness determination for AED deployment;

FIG. 3 is a schematic block diagram illustrating a stationary embodimentof an apparatus for independent readiness determination for AEDdeployment;

FIG. 4 is a schematic block diagram illustrating a mobile embodiment ofan apparatus for independent readiness determination for AED deployment;

FIG. 5 is a schematic block diagram illustrating one embodiment of anapparatus for communicating a response action for an AED enclosureevent;

FIG. 6A is a schematic block diagram illustrating another embodiment ofan apparatus for communicating a response action for an AED enclosureevent;

FIG. 6B depicts an administrative interface 600 for configuring accessto the data network 106 and entering data network credentials 211;

FIG. 7 is a schematic block diagram illustrating additional details ofthe embodiment of FIG. 6A;

FIG. 8 is a schematic flow chart diagram illustrating one embodiment ofa method for independent AED readiness determination for automatedexternal defibrillator deployment; and

FIG. 9 is a schematic flow chart diagram illustrating another embodimentof a method for an independent AED readiness determination for automatedexternal defibrillator deployment.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, method, and/or program product.Accordingly, embodiments may take the form of an entirely hardwareembodiment, an entirely software embodiment (including firmware,resident software, micro-code, etc.), or an embodiment combiningsoftware and hardware aspects that may all generally be referred toherein as a “circuit,” “module,” “component,” “controller,” “block,” or“system.” Furthermore, embodiments may take the form of a programproduct embodied in one or more computer readable storage devicesstoring machine-readable code, computer readable code, and/or programcode, referred hereafter as code. The storage devices may be tangible,non-transitory, and/or non-transmission. The storage devices may notembody signals. In a certain embodiment, the storage devices only employsignals for accessing code.

Many of the functional units described in this specification have beenlabeled as modules, components, controllers, and blocks, to moreparticularly emphasize their implementation independence. For example, amodule, component, controller, block, or system may be implemented as ahardware circuit comprising custom VLSI circuits or gate arrays,off-the-shelf semiconductors such as logic chips, transistors, or otherdiscrete components. A module, component, controller, block, or systemmay also be implemented in programmable hardware devices such asfield-programmable gate arrays, programmable array logic, programmablelogic devices, or the like. Certain functional units described in thespecification are specifically named and may be implemented using one ormore modules, components, controllers, and blocks.

Modules, components, controllers, or blocks may also be implemented incode and/or software for execution by various types of processors. Anidentified module, controller, or block of code may, for instance,include one or more physical or logical blocks of executable code whichmay, for instance, be organized as an object, procedure, or function.Nevertheless, the executables of an identified module, controller,block, or system need not be physically located together but may includedisparate instructions stored in different locations which, when joinedlogically together, include the module and achieve the stated purposefor the module, component, controller, or block.

Indeed, a module, component, controller, or block of code may be asingle instruction, or many instructions, and may even be distributedover several different code segments, among different programs, andacross several memory devices. Similarly, operational data may beidentified and illustrated herein within modules, components,controllers, or blocks, and may be embodied in any suitable formand/organized within any suitable type of data structure. Theoperational data may be collected as a single data set or may bedistributed over different locations including over different computerreadable storage devices. Where a module, component, controller, orblock, or portions thereof are implemented in software, the softwareportions are stored on one or more computer readable storage devices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(RAM), a read-only memory (ROM), an erasable programmable read-onlymemory (EPROM or Flash memory), a portable compact disc read-only memory(CD-ROM), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a computer readable storage medium may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be written in anycombination of one or more programming languages including anobject-oriented programming language such as Python, Ruby, Java,Smalltalk, C++, or the like, and conventional procedural programminglanguages, such as the “C” programming language, or the like, and/ormachine languages such as assembly languages. The code may executeentirely on a user's computer, partly on a user's computer, as astand-alone software package, partly on a user's computer and partly ona remote computer, or entirely on the remote computer or server. In thelatter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, components, controllers, or blocks, userselections, network transactions, database queries, database structures,hardware modules, components, controllers, or blocks, hardware circuits,hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. This code may be provided to a processor of ageneral-purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, another programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus, orother devices to produce a computer implemented process such that thecode, which executes on the computer or other programmable apparatus,provides processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods, and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, component, controller, block, segment, or portion ofcode, which includes one or more executable instructions of the code forimplementing the specified logical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block diagram may occur out of the order noted inthe Figures. For example, two blocks of a block diagram shown insuccession may be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. Other steps and methods may be conceived thatare equivalent in function, logic, or effect to one or more blocks, orportions thereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

AEDs are becoming more and more ubiquitous in public places. AlthoughAEDs are used infrequently, many sudden cardiac arrest emergencies occurin which the use of an AED is a matter of life or death. The timerequired to retrieve an AED and reach a victim of a sudden cardiacarrest dramatically affects the victim's chance of survival.

AED placement is a vital key in AED Program Implementation and providingthe best chance of an SCA victim's survival. When a person goes intoSCA, the chance of survival drops by 10% every 60 seconds that passeswithout defibrillation. As many as twenty percent of AEDs currentlyinstalled are not properly maintained and may not function when deployedin an emergency.

Some public places are encouraged or required to accept donations ofautomated external defibrillators in sufficient quantities to ensurereasonable availability for use during perceived sudden cardiac arrestemergencies. Yet, a significant number of AEDs installed in variousplaces have expired pads, dead batteries, or are otherwise notoperational.

In some instances, an AED is installed in a location but the readinessof the AED is not checked in accordance with a predetermined schedule.One possible option for trying to ensure the readiness of the AED is topay a management service to physically check the AED periodically tomake sure it is in good working order. At the same time, some persons ata particular location may be unaware of AED maintenance guidelinesand/or regulations. Additionally, certain persons responsible for aparticular location may have concerns about the expenses associated withpaying an AED management service.

Another concern with certain AED installations is that sometimes, an AEDis missing from a cabinet or other location where it is expected to bemaintained. If an emergency occurs and a would-be responder attempts toobtain an AED from an expected location and discover that the AED ismissing from the cabinet or other location where the AED is expected tobe maintained, the potential rescue that could have been effectuatedthrough the use of the AED is thwarted.

Another potential option for trying to ensure the readiness of an AED isto integrate circuitry and/or software into a newly developed AED toallow for electronic monitoring of the AED's readiness, through awireless network. Yet, such an option does not address concerns aboutentering the readiness of existing AEDs that have already beeninstalled/deployed in the field.

FIG. 1 is a schematic block diagram illustrating one embodiment of asystem 100 for independent readiness determination for AED deployment.In one embodiment, the system 100 includes mobile communication devices102, AED readiness apparatuses 104, data networks 106, servers 108, andremote communication devices 110. In one embodiment, the AED readinessapparatus 104 is disposed within an AED enclosure 112 that is configuredto hold an AED 114. In some embodiments, at least a portion of the AEDreadiness apparatus 104 is implemented within one or more of the mobilecommunication devices 102. In certain embodiments, at least a portion ofthe AED readiness apparatus 104 is implemented in the server 108.

Even though a specific number of mobile communication devices 102, AEDreadiness apparatuses 104, data networks 106, servers 108, and remotecommunication devices 110 are depicted in FIG. 1, one of skill in theart will recognize that any number of mobile communication devices 102,AED readiness apparatuses 104, data networks 106, servers 108, andremote communication devices 110 may be included in the system 100.

In one embodiment, the term “mobile communication device” refers to oneor more devices such as cellular phones, tablet computers, laptopcomputers, personal digital assistants (“PDA”s), tablet computers,multifunction vehicle consoles, smart watches, radios, streamingdevices, or the like. In some embodiments, the mobile communicationdevice 102 access the data network 106 directly using a networkconnection. In certain embodiments, the mobile communication device 102may be one or more wearable devices such as smart watches, opticalhead-mounted displays, or the like.

In various embodiments, the AED readiness apparatus 104 is disposedwithin an AED enclosure 112 that is configured to hold an AED 114. Invarious embodiments, the AED enclosure 112 may be a hinged cabinet withthe door, an open cabinet, a recessed cabinet, a rotating cabinet, asleeve, a cupboard, a closet, or similar housing for an AED.

In one embodiment, the AED readiness apparatus 104 is configured toobtain event data for an AED enclosure event, where the AED enclosureevent corresponds to the AED 114 registered to be disposed within theAED enclosure 112. In the embodiment, the AED readiness apparatus 104 isfurther configured to classify the AED enclosure event into apredetermined event category and to communicate a response action, inresponse to the AED enclosure event. In this manner, the AED readinessapparatus is used for providing independent readiness determination forautomated external defibrillator deployment.

In certain embodiments, one or more of the mobile communication devices102 includes an embodiment of the AED readiness apparatus 104. In someembodiments, one or more of the mobile communication devices 102communicates with the AED readiness apparatus 104 over the data network106. In various embodiments, at least a portion of the AED readinessapparatus 104 is implemented within the server 108. In some embodiments,the server communicates with one or more of the mobile communicationdevices 102 and/or with an embodiment of at least a portion of the AEDreadiness apparatus 104 disposed within the AED enclosure 112. Furtherdetails regarding the structures and functions of various embodiments ofthe AED readiness apparatus 104 are provided below with respect to FIGS.2-7.

The data network 106, in one embodiment, includes a digitalcommunication network that transmits digital communications. In someembodiments, the data network 106 includes a wireless network such as anarrow band wireless data network, wireless cellular network, localwireless network, such as a Wi-Fi network, a Bluetooth® network, a nearfield communication (“NFC”) network, and ad hoc network (composed ofindividual devices communicating with each other directly), and/or thelike. In certain embodiments, the data network 106 may include a widearea network (“WAN”), a storage area network (“SAN”), a local areanetwork (“LAN”), an optical fiber network, the Internet, or anotherdigital communication network.

The data network 106 may in some embodiments, include one or moreservers 108, one or more access points 109, routers, switches, and/orother networking equipment. In certain embodiments, an AED readinessapparatus 104 disposed within an AED enclosure 112 is configured toperiodically wake and connect to the data network 106 via the one ormore access points 109. In some embodiments, the AED readiness apparatus104 connects and authenticates to the data network 106 via the one ormore access points 109. In certain embodiments, the data network 106also includes computer readable storage media such as a hard disk drive,an optical drive, nonvolatile memory, RAM, or the like.

In one embodiment, the data network 106 includes two or more networks.In various embodiments, the data network 106 may include a radio networkthat transmits digital and/or analog signals. In certain embodiments,the data network 106 is a peer-to-peer network or an ad hoc network thatmay be formed between two or more radios, two or more cellular phones,and/or two or more vehicle communication devices. In some embodiments,the data network 106 includes satellite communications.

The server 108, in some embodiments, includes more than one server. Invarious embodiments, the server 108 includes web services, cloudservices, backend services, and/or application programming interfaces(“APIs”), web APIs, and the like. In certain embodiments, the server 108includes processing services, storage services, application-specificrules engines, and so forth.

In FIG. 1, the remote communication device 110 is depicted, in oneembodiment, as a desktop personal computer (“PC”). In some embodiments,the remote communication device 110 may be a smart phone, a tabletcomputing device, a radio, a wearable computing device, a dispatchconsole, a vehicle computing device, or any similar communication deviceconfigured to communicate over the data network 106. In someembodiments, the remote communication device 110 is a mobilecommunication device 102.

In one embodiment, the remote communication device 110 is locatedoff-premises (also sometimes called “off-premise”) from the mobilecommunication device 102 and/or the AED readiness apparatus 104. Inother embodiments, the remote communication device is located on thesame premises (sometimes referred to as “on-premise”) near the mobilecommunication device 102 and/or the AED readiness apparatus 104. In someembodiments, the term “remote communication device” refers to acommunication device that communicates with the AED readiness apparatus104 which is disposed within the AED enclosure 112. In otherembodiments, the term “remote communications device” refers to acommunication device that communicates with the AED readiness apparatus104 which is implemented at least in part within the mobilecommunication device 102.

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus 200 that may be used for independent readiness determinationfor AED deployment. The apparatus 200 includes one embodiment of the AEDreadiness apparatus 104. In one embodiment, the AED readiness apparatus104 includes a controller 202 configured to detect an AED enclosureevent corresponding to an AED registered to be disposed within AEDenclosure, where the controller 202 is configured to obtain AEDenclosure event data for classification into a predetermined eventcategory, and a communication interface 204 configured to communicate aresponse action in response to the AED enclosure event satisfyingpredetermined criteria for the predetermined event category. In someembodiments, the AED readiness apparatus 104 includes a power source214. In various embodiments, the AED readiness apparatus 104 includesone or more sensors 212, a memory 206, code 208, and data 210 that maybe stored with the memory 206.

In certain embodiments, the code 208 may include a fleet reset module216 that is configured to enable one or more AED readiness apparatuses104 to reset data network credentials 211 in response to a credentialupdate command. In various embodiments, the code 208 may include arescue module 218 that enabled the one or more AED readiness apparatuses104 to periodically connect with the data network 106 to communicatedata related to AED enclosure events to devices connected to the data

In certain embodiments, the AED readiness apparatus 104 is configured toconnect to the data network 106 using the data network credentials 211.In such embodiments, the data network credentials 211 may include one ormore primary credentials 211 a, one or more secondary credentials 211 b,and rescue credentials 211 c. In various embodiments, the data networkcredentials are used to authenticate the AED readiness apparatus 104 tothe data network 106.

In certain embodiments, communicating the response action may includesending a message such as a text message, an application notification,an SMS, an audible tone, a recorded voice message, etc. For example, inone embodiment, the response action includes sending a message inresponse to detecting an AED enclosure event such as a maintenance eventin which the controller 202 detects that pads of the AED have exceededan expiration date. The message, in one embodiment, may be a textmessage or voice message indicating that the pads of the AED will soonbe approaching the expiration date or have passed the expiration date.In some embodiments, the response action may be to automatically placean order for new pads based on a predetermined automatic order profile.

In various embodiments, the controller 202 is configured to communicatethe AED enclosure event data to the server 108 which includes a rulesengine that is configured to perform classification according topredetermined rules for different types of AED enclosure events. Invarious embodiments, the rules engine may be implemented using rulemanagement system services on a server that provides the ability toregister, define, classify, and manage all the rules used in classifyingthe AED enclosure events and communicating response actions to acommunication device. The rule management system may further verify theconsistency of rule definitions and the relationship between differentroles as well as determining specific software components orapplications that interact with one or more of the rules. In certainembodiments, the rules engine is implemented using database queries,statistical analysis, lookup tables, logical rule hierarchy, or similaralgorithms. In certain embodiments, the rules engine performs one ormore of the functions of the apparatuses 200, 300, 400, 500, and/or 600.In various embodiments, the rules engine performs algorithms thatinclude one or more of the steps of the methods 800 and/or 900.

As used herein, the term “AED registered to be disposed within the AEDenclosure” means that the AED 114 is assigned, logged, listed, recorded,enrolled, and/or similarly designated to be disposed within the AEDenclosure.

In some embodiments, referred to herein as “stationary embodiments,” theAED readiness apparatus 104 is configured to be disposed within an AEDenclosure, such as, for example, the AED enclosure 112 depicted inFIG. 1. One example of a stationary embodiment is the AED readinessapparatus 304 depicted in FIG. 3 and described below in more detail withrespect to FIG. 3. As used herein, the term “stationary” meansconfigured to remain in a particular location during operation. At thesame time, stationary embodiments (e.g., the AED readiness apparatus304) may be installed, removed, transferred, or updated at variouslocations and within various AED enclosures 112.

In various stationary embodiments, the controller 202 is selected fromany known controller capable of executing computer readable code 208and/or capable of performing logical operations, such as, for example, amicrocontroller, microprocessor, central processing unit (“CPU”), afield-programmable gate array (“FPGA”), or similar programmablecontroller. In some stationary embodiments, the controller 202 iscommunicatively coupled to the communication interface 204, a memory206, sensors 212, and a power source 214.

In certain stationary embodiments, the communication interface 204includes a wireless transceiver and/or wireless control circuitry thatimplement one or more of various wireless communications methods, suchas, for example, a narrow band wireless, Wi-Fi, Bluetooth®, BluetoothLow Energy (“BLE”), Near-field communication (“NFC”), Radio-frequencyidentification (“RFID”), Zigbee®, Z-wave®, 6LowPAN®, Thread®, GlobalSystem for Mobile communications (“GSM”), 3G/4G/5G/etc., wireless mobiletelecommunications, SigFox®, Neul®, LoRaWAN®, sensor-specific wirelesscommunications, and so forth. Such low power wireless communicationsprovide communication of AED enclosure data while preserving battery ofsensors or AED readiness apparatuses and components thereof. In certainstationary embodiments, the communication interface 204 includes morethan one wireless transceiver and/or wireless control circuitry toimplement more than one wireless communication method.

In other embodiments, referred to herein as “mobile embodiments,” theAED readiness apparatus 104 is implemented in the mobile communicationdevice 102. Examples of a mobile embodiment are the AED readinessapparatuses 404, 504, 604, depicted in FIGS. 4, 5, and 6 and describedin more detail below with respect to FIGS. 4, 5, and 6. In certainmobile embodiments, the mobile communication device 102 in which thecontroller 202 and the communication interface 204 are implemented areexternal to the AED enclosure 112, but are configured to capture AEDenclosure events including AED readiness indicators using a sensor 212such as an optical sensor 418 and/or a user interface 420.

In various mobile embodiments, the controller 202 includes executablecode 208 such as software modules, or blocks of code that are stored ina memory 206 of the mobile communication device and are executed by aprocessor of the mobile communication device, where the processor of themobile communication device is communicatively coupled to the memory 206of the mobile communication device, sensors 212, and the power source214 of the mobile communication device.

In some mobile embodiments, the controller 202 of the AED readinessapparatus 104 may be configured to collect user input from a userinterface of the mobile communication device 102. For example, a user ofthe mobile communication device 102 inputs data in response to questions410 presented on the user interface such as, for example, “is the AEDpresent within the AED enclosure?,” “does a visual readiness indicatorof the AED indicate that the AED is ready?,” and/or “does an audiblereadiness indicator of the AED indicate that the AED is not ready?” suchas, for example, emitting a beeping sound indicating that the battery ofthe AED needs to be replaced soon with the freshly charged battery.

The memory 206, in various stationary embodiments and mobileembodiments, is a computer readable storage medium. In some embodiments,the memory 206 includes volatile computer storage media. For example,the memory 206 may include a RAM, including dynamic RAM (“DRAM”),synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In someembodiments, the memory 206 includes non-volatile computer storagemedia. For example, the memory 206 may include a hard disk drive, aflash memory, battery-backed SRAM, or any other suitable non-volatilecomputer storage device.

In certain embodiments, the memory 206 includes both volatile andnon-volatile computer storage media. In some embodiments, the memory 206stores code 208 and data relating to AED enclosure events and/or AEDreadiness. In some embodiments, the memory 206 also stores program codeand related data, such as an operating system or other controlleralgorithms performed by the controller 202 in certain stationaryembodiments or various mobile embodiments, performed by a processor ofthe mobile communication device.

In various stationary embodiments, at least a portion of the sensors 212are configured to be disposed within an AED enclosure such as the AEDenclosure 112 depicted in FIG. 1 and FIG. 3. More details about thesensors 212 which are configured to be disposed within the AED enclosureare provided below with respect to FIG. 3.

In certain mobile embodiments, the sensors 212 may include a sensor suchas an optical sensor, an RFID sensor, an NFC interface, a Bluetooth®interface, a Wi-Fi interface, or a similar device, implemented in themobile communication device 102 for scanning, reading, writing, orand/or otherwise interacting with an AED identifier and/or an AEDenclosure identifier. The sensors 212 in certain mobile embodimentsfurther include wireless sensors disposed within the AED enclosure,where the wireless sensors are communicatively coupled to the controller202 through the communication interface 204 to the processor of themobile communication device 102.

The power source 214, in various stationary embodiments, includes abattery and/or circuitry for determining a status of the battery, suchas, for example, voltage, operating current, remaining charge within thebattery, and so forth. In certain mobile embodiments, the power source214 includes multiple power sources such as the power source of themobile communication device and/or a power source of any sensors 212configured to be disposed within the AED enclosure 112. The power source214 in various mobile embodiments includes circuitry, such as a batterysensor, for determining a status of the power source of the sensors 212that are wireless such as, for example, voltage, operating current,remaining charge within a battery of the sensor, and so forth.

In one mobile embodiment of the AED readiness apparatus 104 (such asdepicted in FIG. 4), a first instance of the AED readiness apparatus 104is configured to determine whether the AED enclosure 112 includes astationary embodiment of a second instance of the AED readinessapparatus 104 in which the controller 202 is disposed within the AEDenclosure 112 (such as depicted in FIG. 3). In such an embodiment, theAED readiness apparatus 404 is configured to communicate a responseaction to facilitate configuration of the AED enclosure with an updatedcontroller configured to collect the sensor data from at least onesensor 212 that is disposed within the AED enclosure. In one embodiment,the updated controller is implemented within an updated mobileembodiment to read sensor data from a sensor 212 that is a wirelesssensor disposed within the AED enclosure 112. In another embodiment, theupdated controller is implemented as a stationary embodiment of the AEDreadiness apparatus (e.g., 304) configured to be disposed within the AEDenclosure 112.

In some embodiments, a mobile embodiment of the AED readiness apparatus104 is configured to independently confirm that a stationary embodimentof the AED readiness apparatus 104 is operating correctly. In certainembodiments, AED enclosure event data is collected from more than onemobile embodiment of the AED readiness apparatus 104 and is aggregated.Further details regarding AED enclosure event data are described belowwith respect to the stationary embodiment of the AED readiness apparatus304 depicted in FIG. 3 and the mobile embodiment of the AED readinessapparatus 404 depicted in FIG. 5.

FIG. 3 is a schematic block diagram illustrating a stationary embodimentof an apparatus 300 for independent readiness determination for AEDdeployment. In one embodiment, the AED readiness apparatus 304 is astationary embodiment that includes an instance of the AED readinessapparatus 104 and is configured to be disposed within the AED enclosure112. In one embodiment, the AED readiness apparatus 304 includes acontroller 202, such as a processor as described above, and acommunication interface 204 that includes a wireless transceiver and/orwireless control circuitry. In various embodiments, the AED readinessapparatus 304 includes the memory 206, the code 208, (including, forexample, code for the controller 202, the communication interface 204,the sensors 212, the fleet reset module 216, and/or the rescue module218), the data 210 (including, for example, the data network credentials211), the sensors 212, and the power source 214, substantially asdepicted in FIG. 2 and described above with respect to variousstationary embodiments.

In various embodiments, the AED readiness apparatus 304 includes one ormore sensors 212, such as for example, an access sensor 308, an objectsensor 310, an input transducer 312, an optical sensor 314, a humiditysensor 316, and a temperature sensor 318 that are used to collect one ormore AED readiness parameters. In some embodiments, the AED readinessapparatus 304 includes a battery sensor 319 that senses a status of abattery within the power source 214. In various embodiments, the AEDreadiness apparatus includes an output transducer 320.

In certain embodiments, the controller 202 is further configured tocollect one or more AED readiness parameters such as an individualenclosure identifier, an individual AED identifier, an enclosure accessindicator, an AED presence indicator that indicates whether the AED ispresently disposed correctly within the AED enclosure, an audiblereadiness indicator of the AED, a visual readiness indicator of the AED,and a storage environment indicator that indicates a storage environmentparameter such as temperature and/or humidity within the AED enclosure.

In one embodiment, the controller 202 is configured to collect theindividual enclosure identifier and the individual AED identifier of theAED registered to be disposed within the AED enclosure using a sensorand/or a user interface of a mobile communication device 102. Forexample, when an AED is installed and/or registered to be disposedwithin a particular AED enclosure, in one embodiment, the controllercollects the individual identifier using a sensor such as an opticalsensor (e.g., a camera or bar code reader), an RFID reader, or anothersensor, to collect the individual enclosure identifier and theindividual AED identifier of the AED. In some embodiments, theindividual identifier is associated with a bar code, a QR code, an RFIDtag, and/or a similar label scanned by the mobile communication device.In other embodiments, the controller 202 is configured to collect theindividual enclosure identifier and the individual AED identifier of theAED using the user interface of the mobile communication device (e.g.,by entering the individual identifiers using the user interface).

In various embodiments, the individual AED enclosure identifier and theindividual AED identifier may be multidimensional data structures thatinclude various fields such as names, geographic locations, and/or anycombination of data fields. For example, where the individual enclosureidentifier includes a geographic location, the controller 202 maycollect the geographical location using a geolocation module of themobile communication device. It may be noted that in both stationaryembodiments and mobile embodiments, the controller 202 may be configuredto collect the AED readiness parameters using the sensors 212 and/orusing the mobile communication device's sensors and/or user interface.

In one embodiment, the controller 202 is configured to collect anenclosure access indicator that indicates whether the AED enclosure isopen using the access sensor 308. In various embodiments, the accesssensor 308 is selected from various types of sensors and/or switchessuch as pushbutton switches, optical sensors, magnetic sensors, and thelike. In certain embodiments, the AED readiness apparatus 304 isconfigured to wake the controller 202 from a dormant mode to an activemode in response to the access sensor 308 determining that the accessdoor is open. For example, in one embodiment, the access sensor 308 isconfigured to be normally open (i.e., electrically disconnected) if theAED enclosure is closed and closed if the AED enclosure is open. If theenclosure door is closed, an electrical path through the access sensor308 is open so that power from the power source 214 is beneficiallyconserved to prolong battery life. In response to the AED enclosurebeing opened, the electrical path through the access sensor 308 closes,thus waking the controller 202 from a dormant mode to an active mode. Invarious embodiments, multiple levels of power control may be configuredfor optimization of power usage under predetermined circumstances.

For example, in one embodiment the access sensor 308 includes a magneticswitch/sensor that is normally open if proximate to a magnetic field andclosed if moved away from the magnetic field. In certain embodiments, amagnet 324 is coupled to an interior surface of an enclosure door of theAED enclosure 112 to move in or out of proximity with the access sensor308 in response to the enclosure door closing or opening. In addition tothe low-power benefits of a normally-open magnetic switch, the magneticswitch has a higher mechanical reliability than certain mechanicalswitches which beneficially improves the reliability of the AEDreadiness apparatus 304 for independently determining the readiness ofthe AED 114 for deployment in a sudden cardiac arrest emergency, thusimproving the ability to save lives.

In one embodiment, the controller is configured to collect theAED-presence indicator that indicates whether the AED 114 is presentlydisposed correctly within the AED enclosure 112 using an object sensor310. In various embodiments, object sensor 310 includes a time-of-flightsensor configured to measure a reflected signal distance to determinewhether the AED 114 is disposed within the AED enclosure 112. Forexample, in one embodiment the object sensor 310 includes alaser-ranging sensor that measures a reflected signal distance to theAED 114. If the AED 114 is presently removed from the AED enclosure 112,the reflected signal has a longer time-of-flight than if the AED 114 ispresently disposed within the AED enclosure 112.

In certain embodiments, the object sensor 310 senses a particularportion of the AED 114, such as, for example, a handle portion that isdisposed nearer to a front surface of the AED 114. Accordingly, if theAED 114 is disposed backwards within the AED enclosure 112 so that avisual readiness indicator 328 (including, for example, a display 332)of the AED 114 are not visible through a window 330 of AED enclosure112, the object sensor 310 determines that the AED 114 is positionedincorrectly within the AED enclosure 112. In various embodiments, theobject sensor 310 uses infrared, ultrasonic, or any other type ofelectromagnetic signal to determine the reflected signal distance to theAED 114.

In some embodiments, the object sensor 310 includes any of several typesof sensors, such as, for example, a strain gauge or any weight sensorthat senses the weight of the AED 114 if presently disposed correctlywithin the AED enclosure 112. In other embodiments, the object sensor310 includes a mechanical or optical switch that closes or opens asignal path used to determine whether the AED 114 is presently disposedcorrectly with the AED enclosure 112.

In one embodiment, the controller 202 is configured to collect anaudible readiness indicator (e.g., a sound such as a beeping or chirpingsound emitted by a buzzer, speaker, or transducer 326 of the AED 114)that indicates whether the AED 114 is ready for deployment. For example,an AED may be configured to emit an audible warning in response to abattery charge level being below a predetermined level, a pad electrodethat has come unplugged, a failed self-test, and the like. In someembodiments, the controller 202 communicates with an input transducer312 to capture audio data from the audible readiness indicator.

In some embodiments, the AED readiness apparatus 304 further includes afilter that distinguishes the audible readiness indicator from soundsthat fail to satisfy predetermined parameters for the audible readinessindicator. In certain embodiments, the filter performs frequency domainprocessing and time domain processing on the audio data captured by theinput transducer to distinguish the audible readiness indicator from thesounds that fail to satisfy the predetermined parameters for the audiblereadiness indicator.

As one example, in one embodiment, the AED 114 is configured to emit abeep sound having a particular tone or tones at specific intervals(e.g., 15 seconds, 90 seconds) in response to a battery level of the AED114 having a charge level high enough to operate correctly but needingto be replaced within a predetermined period. Another AED from adifferent manufacturer may advise a user not to deploy an AED if it isemitting any type of tone. The AED 114 may also be configured to performautomatic self-tests at regular time intervals (e.g., daily, weekly, ormonthly). In some embodiments, if the AED 114 detects an error, thetransducer 326 is configured to emit a beep sound every 30 seconds.Thus, the filter of the AED readiness apparatus 304 is, in variousembodiments, beneficially configured to distinguish different tonesand/or patterns based on manufacturer specifications. Such manufacturerspecifications are, in certain embodiments, configured to be accessedfrom the server 108 and to be updated from time to time.

Furthermore, certain other apparatuses in proximity to the AED 114and/or the AED enclosure may also emit sounds such as beep sounds. Forexample, if the AED 114 is disposed near an entrance/exit detector or anelevator door that emits an audible readiness indicator, the filter maydistinguish the tone or pattern of the AED audible readiness indicatorfrom sounds emitted by the other apparatuses, thus reducing thelikelihood of the AED readiness apparatus 304 communicating a responseaction base on a misidentified sound. In various embodiments, the filterof the AED readiness apparatus 304 utilizes Fast Fourier Transformtechnology to determine a tone of the audible readiness indicator.

In one embodiment, the controller 202 is configured to collect a visualreadiness indicator of the AED 114 using a sensor 212 such as an opticalsensor 314. For example, if the visual readiness indicator 328 of theAED 114 is communicated by emission or reflection of light having apredetermined color, brightness, and/or pattern, the optical sensor 314,in certain embodiments, detects the predetermined color, brightness,and/or pattern of the light. For example, in certain embodiments, theAED 114 includes a visual readiness indicator 328 that is configured toemit or reflect green light if the AED 114 is in a state of readinessand configured to emit or reflect red light if the AED 114 is not in astate of readiness. In some embodiments, the AED 114 is configured toemit the predetermined color of light using a predetermined pattern ofblinks to attract attention.

In various embodiments, the optical sensor 314 is any of varioustechnologies such as photodiode, phototransistor, cadmium sulfide cell,or similar technologies to detect the light. In some embodiments, theoptical sensor 314 includes an array of optical detectors such as foundin a digital imaging array and/or camera. In certain embodiments, thevisual readiness indicator 328 of the AED 114 is communicated using anopen pattern in response to the AED being in a state of readiness and anX-shaped or crossed-out pattern in response to the AED not being in astate of readiness. In some embodiments, the visual readiness indicator328 includes the display 332 that displays a readiness status of the AED114.

Exposure of an AED 114 to a temperature the exceeds or falls below arecommended temperature range is certain embodiments, affects batterylife, and/or potentially operation of the AED 114. Similarly, exposureof the AED 114 to excessively humid environments also affects thebattery life and/or potentially, the operation of the AED 114. In oneembodiment, the controller 202 is configured to collect a storageenvironment indicator that indicates the temperature and/or the humidityof the environment within the AED enclosure 112 using a temperaturesensor 318 and/or a humidity sensor 316. For example, the temperaturesensor 318 includes one or more thermocouples, digital temperaturesensors, or the like. In some embodiments, the temperature sensor 318 isintegrated with the humidity sensor 316 into a single integrated circuitpackage.

In certain stationary embodiments, various of the sensors 212 (includingthe access sensor 308, an object sensor 310, an input transducer 312, anoptical sensor 314, a humidity sensor 316, and a temperature sensor318), are disposed within the AED enclosure 112, thus offering a degreeof protection from the elements and/or from electrical, mechanical, orhuman interference.

In some embodiments, including in certain mobile embodiments, various ofthe sensors 212 are implemented as wireless sensors that may be accessedby the controller 212 as implemented in the mobile communication device102 using a wireless connection, such as Bluetooth, Wi-Fi, and/orvarious other types of wireless communications as described above withrespect to the AED readiness apparatus 104 of FIG. 2.

In other embodiments, including various mobile embodiments, some of thesensors 212 such as the optical sensor 314 and/or the input transducer312 are implemented within the mobile communication device 102. Forexample, the mobile communication device 102 may include an instance ofthe AED readiness apparatus 104 in which the controller 202 isimplemented using code executed by a processor of the mobilecommunication device 102, where the mobile communication device 102 usesa microphone of the mobile communication device 102 to collect databeing emitted by the AED 114. Similarly, in certain mobile embodimentsin which the controller 202 is implemented in the mobile communicationdevice 102, the controller 202 may use a camera of the mobilecommunication device together with color and/or pattern recognitionsoftware to distinguish the readiness status indicated by various visualreadiness indicators of the AED 114.

FIG. 4 is a schematic block diagram illustrating a mobile embodiment ofan apparatus 400 for independent readiness determination for AEDdeployment. In one embodiment, the apparatus 400 includes a mobilecommunication device 102 and an AED readiness apparatus 404 thatincludes one instance of an AED readiness apparatus 104 with acontroller 202 and a communication interface 204. In variousembodiments, the AED readiness apparatus 404 is a mobile embodimentmeaning that the controller 202 and the communication interface 204 areimplemented within the mobile communication device 102 which is externalto the AED enclosure.

In some situations, the AED 114 is deployed in a location such as ashopping mall, and office, or school, where hundreds of people may walkby one or more AEDs 114 every day. In such situations, providing the AEDreadiness apparatus 404 as a mobile embodiment implemented in smartphones, smart watches, or other mobile communication devices, improvesthe accessibility and approachability of the AED 114 by the persons mostlikely to use them in a rescue (e.g., an SCA emergency). One method ofimproving accessibility and approachability of the AED 114 is to engagesuch persons in performing AED readiness checks using the user interface420 of the mobile communication device 102 as depicted in FIG. 4.Accessibility is improved by increasing public awareness of the locationof the AED in the public space and approachability is increased byincreasing awareness within likely responders that the AED 114 isdesigned to be usable by a layperson to save a life.

In one embodiment, the controller 202 of the AED readiness apparatus 404is implemented in the mobile communication device which includes a userinterface 420 configured to collect the one or more AED readinessparameters through the user interface 420. of the mobile communicationdevice 102. In the embodiment, the user interface 420 is a touchscreendisplay that is configured to display one or more questions to which auser of the mobile communication device responds by touching apredetermined button, checkbox, and/or another input mechanism of theuser interface 420.

In certain embodiments, the controller 202 of the AED readinessapparatus 404 is configured to collect an AED enclosure identifier inresponse to a user of the mobile communication device 102 scanning ascannable representation of a portion of the AED enclosure identifier322 such as a barcode, a QR code, an RFID tag, etc., which is attachedto the AED enclosure 112 using, for example, the optical sensor e.g., acamera of the mobile communication device 102.

The controller 202 communicates the AED enclosure identifier to adatabase, such as a database stored in the server 108 so that dataentered using the user interface 420 is identified as corresponding tothe particular AED enclosure 112 and/or the AED 114 registered to bedisposed within the AED enclosure 112.

The user interface 420 is beneficially configured to minimize the timeneeded to collect the user input. In certain embodiments, the userinterface 420 is configured to recognize one-touch responses toreadiness queries presented via the user interface 420.

In various embodiments, the user interface 420 displays a graphicalrepresentation of the AED 114 showing the location and appearance of thevisual readiness indicator 328 corresponding to a particular model ofthe AED 114 which is registered to be disposed within the AED enclosure112. Similarly, the user interface 420 in some embodiments emits a soundrepresentative of the audible readiness indicator corresponding to theparticular model of the AED 114 is configured to facilitate a userperforming a readiness check to recognize a predetermined audiblereadiness indicator.

In some embodiments, the user interface displays a query requesting auser of the AED readiness apparatus 404 to determine where the userinterface whether the AED location 412 shown on a map and/or displayedtextually is correct.

In various embodiments, the controller 202 is configured to perform acomparison of user input data collected through the user interface 420and sensor data collected by the controller 202 or by a second instanceof the controller 202 implemented within a stationary embodiment (e.g.,as depicted in FIG. 3 with respect to the AED readiness apparatus 304)in which at least one of the sensors 212 is disposed within the AEDenclosure 112 and/or a mobile embodiment (e.g., as depicted in FIG. 4with respect to the AED readiness apparatus 404) which at least one ofthe sensors to 12 is disposed within the AED enclosure 112 and thecontroller is implemented within the mobile communication device 102where the communication interface 204 of the AED readiness apparatuscommunicates via wireless communication with at least one of the sensors212. In various such embodiments, the controller 202 is furtherconfigured to communicate results of the comparison to a mobilecommunication device 102 and/or to a second communication device such asthe remote communication device 110 which may be a computer, a dispatchconsole, a mobile communication device, or any communication deviceconfigured to receive communications over the data network 106.

In some embodiments, the user input data and/or the sensor data areaggregated to provide aggregate results and/or statistical results for aparticular group, location, AED model, AED make, user profile, sensortype, or any predetermined grouping of user input data and/or sensordata. Various such embodiments improve AED readiness checking technologyby providing multiple independent sources of AED readiness data forvarious predetermined groupings.

In certain embodiments, the controller 202 is configured to collect userinput data through the user interface 420 of the mobile communicationdevice 102 and is further configured to communicate the response actionto facilitate configuration of the AED enclosure with an updatedinstance of the controller 202 configured to collect the sensor datafrom at least one of the one or more sensors 212 disposed within the AEDenclosure. For example, in one mobile embodiment, the AED readinessapparatus 404 scans a barcode, QR code, RFID tag, and/or similarindividual AED enclosure identifier 322 and determines based that theAED enclosure 112 is not yet configured to include an updated controller202. In some embodiments, the term “updated controller” may refer to acontroller 202 of a stationary embodiment, such as the AED readinessapparatus 304, where the controller 202 and/or certain of the sensors212 are disposed within the AED enclosure 112. Various such embodimentsimprove AED readiness checking technology by enabling particular AEDinstallations to change from not having any internal sensors and/or anyinternal controller disposed within the AED enclosure 112 to an updatedcontroller 202 where at least a portion of the controller 202 includeshardware components disposed within the AED enclosure 112. In otherembodiments, the term “updated controller” refers to a stationaryembodiment of the controller 202 where at least a portion of hardwarecomponents of the controller 202 disposed within the AED enclosure 112are updated to include new features, new sensors, and/or new software.

In other embodiments, the AED readiness apparatus 404 uses an outputtransducer 416 (e.g., a speaker) to play a tone and/or patternrepresentative of the audible readiness indicator of the AED 114. Insome embodiments, the AED readiness apparatus 404 uses the outputtransducer 416 of the mobile communication device the input transducer312 to present a voice query to the user and uses the input transducer414 of the mobile communication device 102 to determine a voice responsefrom the user of the mobile communication device 102 to the voice query.

To maximize the probability of a successful response to a sudden cardiacarrest emergency, in certain embodiments, it is beneficial to involvemultiple responders so that a first person responding may deploy theAED, while a second person calls a public emergency response service(e.g., a 911 emergency response service in the U.S.) and a third personruns to meet the public emergency responders at an entrance to thebuilding to quickly guide the public emergency responders to thelocation of the SCA emergency, and so forth. In some embodiments, thecommunication interface is configured to communicate response actioncomprising a list of emergency response assignments configured to beselected to be performed by individual responders. For example, such alist may include an assignment to deploy the AED, initiate a phone callto a public emergency response service, meet public emergency respondersat the entrance, and so forth.

Additionally, the likelihood of a successful response to SCA emergencyincreases in various embodiments as more people become aware of thelocation of the AED 114, know how to determine whether the AED 114 isready to be deployed, learn how to deploy the AED 114 in an SCAemergency, know how to administer cardiopulmonary resuscitation (“CPR”),and so forth. Thus, one benefit of the AED readiness apparatus 404 beingimplemented in the mobile communication device 102, is that by engagingvarious potential responders to perform AED readiness checks using theuser interface 420, the readiness status of potential responders ismaximized through increased awareness of the benefits of using the AED114 as well as through increased awareness of how to deploy the AED 114and to deploy other potential responders to the same SCA emergency toperform other roles during the SCA emergency. In some embodiments, theroles are predetermined by responders or users configuring profiles thatdesignate certain roles that the users are ready to fulfill. In otherembodiments, the roles are determined based on the readiness status ofvarious responders to respond to an AED enclosure event of a particularpredetermined category.

FIG. 5 is a schematic block diagram illustrating one embodiment of anapparatus 500 for communicating a response action for an AED enclosureevent. In one embodiment, the apparatus 500 includes an AED readinessapparatus 504 for independent readiness determination for AEDdeployment.

In one embodiment, the AED readiness apparatus 504 includes an instanceof an AED readiness apparatus 104 that is implemented at least in part,in the mobile communication device 102. In other embodiments, the AEDreadiness apparatus 504 includes an instance of an AED readinessapparatus 104 is implemented at least in part as a stationary apparatusthat accesses sensors 212 disposed within the AED enclosure 112substantially as described above with respect to the AED readinessapparatus 304 depicted in FIG. 3.

Various AEDs are designed for use by persons with limited training.Similarly, certain AEDs are designed to provide audible or visualreadiness indicators to persons who are aware that an AED is availableand who know how to interpret the readiness indicators. The inventors ofthe subject matter disclosed herein have determined that use and/ormaintenance of an AED is significantly improved by providing apparatusesand methods that are configured to determine the readiness of the AEDitself and may also determine the readiness of responders to certainpredetermined event categories relating to different types of AEDenclosure events.

For example, in certain embodiments, a predetermined event category foran AED enclosure event is an emergency response event, a maintenanceevent, and/or a fault event. In various embodiments, an emergencyresponse event is detected detecting a removal of the AED from the AEDenclosure to rescue a person experiencing an SCA. In some embodiments,if the AED is not returned to its location within the AED enclosurewithin a predetermined time period, the controller 202 and/or the rulesengine, presumes that the AED enclosure event is an AED emergencyresponse event. A maintenance event, in various embodiments, includesany event related to maintaining the readiness of the AED such as, forexample, battery power remaining, self-tests passed, and so forth and/ormaintaining the readiness of consumables used in deployment of the AEDsuch as, for example, pads, leads, instructions, and so forth.

In certain embodiments, a fault event indicates an event that is notclassified as an emergency event or a maintenance event such as, forexample, tampering with or inadvertently removing the AED from theenclosure. Other types of fault events might include for examplespurious alarms or signals which go off at a time of day in whichpersons are unlikely to be occupying the premises where the AEDenclosure is located. In some embodiments, a fault event is alsoclassified as a maintenance event because certain repair and/ormaintenance actions may be used to address the fault.

In various embodiments, the AED readiness apparatus 504 communicatesdata related to the readiness of a responder to respond to differenttypes of AED enclosure events. In certain embodiments, a mobilecommunication device 102 may be used to help determine the readinessstatus of the responder based on a parameter such as a level of trainingto respond to one or more predetermined categories of AED enclosureevents, a location of the mobile communication device corresponding tothe responder, a user input indicating the readiness of the responder torespond to the relevant event, and/or an AED event response history ofthe responder.

For example, in certain embodiments, the AED readiness apparatus 504 mayinclude a user interface 520 that collects user input 510 indicating thereadiness status of the user to respond to a predetermined AED enclosureevent for a predetermined event category. In some embodiments, userinput 510 is collected to indicate certain event categories (e.g.,emergency response, maintenance, and/or fault) for which the responderwants to receive event notifications. In one embodiment, the user inputincludes a one-touch user input (e.g., a user placing her thumb on abutton or area of a touchscreen) on a user interface element such abutton or even a touch within a certain area that a responder uses toindicate that the AED enclosure event is being responded to either bythe responder using the apparatus 500 or by another responder. Incertain embodiments, when a notification is sent to a responderregarding an emergency response event, a notification is also sent toremote communication devices letting them know which specific respondersreceived the message have indicated that they are responding.

In various embodiments, the user input 510 includes audio (e.g. voice)data collected using a microphone of the mobile communication device102. In some embodiments, a response action is communicated using aspeaker 516 of the mobile communication device 102, such as, forexample, by playing a beep tone, a voice recording, and/or a live voiceproviding the response action.

In some embodiments, the readiness status of the user to respond to thepredetermined enclosure event for the predetermined event category isinput directly by the user. In other embodiments, additional “responderreadiness” data may be stored on the mobile communication device 102 orin the server 108 and may be manually and/or automatically updated fromtime to time. In certain embodiments, the AED readiness apparatus 504compares the AED readiness status of the user to a predeterminedcriteria for the predetermined event category. For example, in responseto an AED enclosure event that that is categorized within thepredetermined event category of maintenance events, the response actioncommunicated to the mobile communication device 102 is communicated toqualified maintenance personnel for a particular brand of AED, a certainAED service company with an agreement to service AEDs within a specifiedregion, an on-site administrator responsible for AED maintenance, and soforth.

Similarly, in response to the controller 202 detecting AED enclosureevent classified as an emergency response event, the AED readinessapparatus 504 communicates the response action to a communication devicesuch as the mobile communication device 102 and/or the remotecommunication device where the communication device corresponds to aresponder (e.g., a user to the communication device) having a readinessstatus that satisfies one or more predetermined event criteria for theemergency response event category. For example, in various embodimentsthe predetermined event criteria may include the readiness status of theresponder such as being within 90 seconds of the AED enclosure, havingcompleted training on AED use, having prior experience responding toemergency events.

In some embodiments, the predetermined event criteria may include theresponder having a readiness status that is indirectly related to AEDuse such as, for example, the responder being certified to performcardiopulmonary resuscitation (“CPR”), being assigned to direct publicemergency responders to a location of the event, user input indicatingreadiness (e.g., opting in or agreeing to be an emergency responder fora particular AED location, organization, etc.).

In some embodiments, the AED enclosure event may be classified as afault event. For example, referring to FIG. 3, if a person removes theAED 114 from the AED enclosure 112 mistakenly believing there is anemergency or being unaware that removal of AED 114 can trigger an AEDenclosure event that is classified and communicated as an emergencyevent, the person may hear an audible signal from the AED readinessapparatus 304 such as an alarm-type sound emitted by the outputtransducer 320 and realize that the AED 114 should be put back in theAED enclosure 112. In response to the person putting the AED 114 back inthe AED enclosure 112, the controller 202 may detect an AED event thatis classified as a fault event and may in response communicate to publicemergency responders that the previously communicated emergency event isno longer classified as an emergency and the public emergency respondersdo not need to respond. In some and embodiments, the term “satisfyingthe predetermined criteria” refers to readiness status data such as areadiness score exceeding a predetermined threshold, and/or fallingwithin a predetermined range, and so forth. Such criteria or anycriteria relevant to AED deployment may be input via the user interfaceof a mobile communication device or by a remote communication devicesuch as an administrator application for an administrator of an AEDfleet, a health office for school or business, or similar management oradministrative role.

In certain embodiments, the AED readiness apparatus 504 is configured tocause a map showing a location of an AED 512 and locations of one ormore responders 522 a, 522 b. In certain embodiments, the responder 522b may be outside a predetermined range such as within 90 secondsrun/walk of the AED and still the communication interface 204communicates a response action to the responder 522 b. For example, at alarge school or workplace, the responder 522 b may be too remote fromthe location of the AED to respond directly within a 90 second timewindow. In some embodiments, if the responder is a health servicesmanager or an organization administrator, the responder may configurethe mobile communication device 102 to receive a communicated responseaction including AED enclosure event data for the event into apredetermined category, showing various responders who can respond morequickly, and so forth.

Referring now to FIG. 6A, FIG. 6B, and FIG. 7 (with certain referencealso to elements depicted and described above with respect to FIG. 1 andFIG. 2), FIG. 6A is a schematic block diagram illustrating oneembodiment of an apparatus 600 for communicating a response action foran AED enclosure event for multiple AED enclosures. FIG. 6B depicts anadministrative interface 600 for configuring access to the data network106 and entering data network credentials 211. FIG. 7 is a schematicblock diagram illustrating one embodiment of another apparatus 700 forcommunicating a response action for an AED enclosure event for anindividual AED enclosure. In one embodiment, the apparatus 600 of FIG. 6includes one instance of a mobile communication device 102 with an AEDreadiness apparatus 604 that includes one instance of an AED readinessapparatus 104 substantially as described above with respect to FIG. 2.In other embodiments, the apparatus 600 includes the mobilecommunication device 102 is configured to receive a communication froman AED readiness apparatus not implemented in the mobile communicationdevice 102 such as, for example, the AED readiness apparatus 304depicted in FIG. 3 or the AED readiness apparatus 404 depicted in FIG.4.

In one embodiment as depicted in FIG. 6A, the apparatus 600 isconfigured to display a map 612 that displays a geographical locationfor multiple AED enclosures depicted as 622 a, 622 b, 622 c . . . and622 n. In certain embodiments, the communication interface of the AEDapparatus 604 or other the AED apparatuses 304, 404, and so forth,communicates a response action such as, for example, a readinessindicator for multiple AEDs e.g., 622 a, 622 b, 622 c . . . and 622 n.For example, in certain embodiments, the response action may cause anAED icon displayed on a user interface 620 to change colors from greento red in response to a controller 202 of the AED apparatus 604 (or ofother the AED apparatuses 304, 404) detecting an AED enclosure eventthat is classified as an emergency response event, a maintenance eventand/or a fault event, such as, for example, an emergency response eventwhere the AED has been removed from the AED enclosure or maintenanceevent where the AED enclosure event is capable of potentially impairingthe readiness of the AED to respond due to an issue with the AED itselfand/or an issue with a consumable such as pads, wires, etc. In certainembodiments, textual information is display in a user input portion 510where the records displayed correspond to AED enclosures 622 a, 622 b,622 c . . . 622 n displayed on the map 612.

In other embodiments, the user interface 620 displays a dashboard thatincludes a list of selected AED enclosures, a description of thelocation, both at a high level such as a street address as well as at amore detailed level such as a particular area of a building, aparticular room, or a particular floor of a multistory building. Suchdetailed information beneficially provides responders to emergencyresponse events and maintenance events with graphical and/or textualinformation that facilitates a response action by a responder whosereadiness status for a particular event category satisfies predeterminedcriteria.

In various embodiments, the user interface 620 displays textualrepresentations which may like the map 612 be grouped hierarchically.For example, in some embodiments, groups of school districts aredisplayed at the highest level of hierarchy, then within a selectedschool district individual schools are displayed at a lower level of thehierarchy, and various rooms within the individual schools are displayedat a more detailed lower level of the hierarchy.

FIG. 6B depicts one embodiment of an apparatus 600 having anadministrative interface 602 for configuring access to the data network106 (depicted in FIG. 1) and entering data network credentials 211depicted in FIG. 2. In certain venues, such as, for example, a businesscampus, an educational campus, a stadium, a convention center, and soforth, multiple AEDs may be deployed in an area serviced by a datanetwork 106 with multiple access points through which an authenticatedwireless device is provided access. To preserve battery life, in variousembodiments, the AED readiness apparatus periodically connects and isauthenticated to the data network 106 by providing recognized datanetwork credentials 211.

Although FIG. 6B depicts the administrator interface 602 as beingimplemented in an application for a mobile communication device 102, invarious embodiments, the administrator interface 602 may be implementedas a web-based service to be accessed for example by a web browser.

One of the challenges of deploying multiple AED readiness apparatuses104 for an organization or venue with commonly shared network resourcesis updating the network credentials on all the devices when a change ismade by the organization or venue. For example, in certain embodiments,an AED readiness apparatus such as the AED readiness apparatus 104 mayuse a venue-wide, business-wide, or educational campus-wide networkaccess system that is protected and requires credentials such as apassword to login to the network. Enabling multiple devices to access aparticular network through multiple mesh access points makes it easierfor mobile users to move about the campus while staying connected andwithout having to enter different passwords for each access point. Itmay be desirable for a venue, business, educational campus, or otherorganization to deploy multiple AED and multiple AED readinessapparatuses 104 that connect to a selected network using a particularpassword.

Furthermore, for security reasons, the administrator may from time totime update the password for accessing the selected network. In certainembodiments, the systems, apparatuses, and/or disclosed herein include afleet reset module 216 that enables for an administrator to ensure thatmultiple AED readiness apparatuses can connect to the selected networkusing the new password without having to go to the location of each AEDenclosure 112 to manually update the password.

In some embodiments, a user may use the administrative interface 602 toenter an administrator username 632 and administrator password 634 to beauthorized to enter data such as data network credentials 211 forconfiguring the fleet reset module 216 included with certain embodimentsof the AED readiness apparatus 104.

In various embodiments, the user may enter a network name 636 or SSIDfor accessing the data network 106. A user may enter or update networkcredentials 211, such as primary credentials 211 a and/or secondarycredentials 211 b, which may be used by the fleet reset module 216and/or the rescue module 218 of the AED readiness apparatus 104. Theprimary credentials 211 a and the secondary credentials 211 b enable auser to pre-configure one or more AED readiness apparatuses for anupcoming change in a network password, which in turn enables the AEDreadiness apparatuses to periodically sleep and wake up to preservebattery life even when a network password is changed before a wake-upprocedure. Further details about the structures and functions of thefleet reset module 216 and the rescue module 218 are provided below withrespect to FIG. 9.

FIG. 7 depicts an apparatus 700 configured to communicate more detailedreadiness status information related to a particular AED enclosureand/or an AED registered to be disposed within the particular AEDenclosure. In one embodiment, the apparatus 700 includes an AEDreadiness apparatus of 704 with one instance of an AED readinessapparatus 104 implemented for example as a mobile embodiment. In otherembodiments, the apparatus 700 includes a mobile communication device102 that receives information from any AED readiness apparatus, such as,for example, the AED readiness apparatus 304, 404, 504, 604, etc.

In certain embodiments, a user interface of the controller 202 of theapparatus 600 is configured to accept a user input such as, for example,a selection of a particular AED icon to display further details aboutthe readiness status of an AED corresponding to the selected AED icon.In other words, in certain embodiments, FIG. 6 depicts an AED readinessdashboard at a high level or macrolevel showing multiple AED enclosuresand FIG. 7 depicts an AED readiness dashboard or AED readiness statusdisplay at a detailed level or individual AED level for a particular AEDenclosure.

In one embodiment, the apparatus 700 includes one instance of a mobilecommunication device 102 with an AED readiness apparatus 704 thatincludes one instance of an AED readiness apparatus 104 substantially asdescribed above with respect to the apparatuses 200, 404, 504, and 604,depicted respectively in FIGS. 2, 4, 5, and 6. In other embodiments, theapparatus 700 communicates data collected by other AED apparatuses suchas, for example, the stationary embodiment of the AED readinessapparatus 304 depicted in FIG. 3. In various embodiments, the apparatus700 displays an AED enclosure identifier that includes a name, a generallocation, a detailed location, and/or and AED readiness indicator 714for AED registered to be disposed with the selected AED enclosure. Invarious embodiments, a spin element 722 of the user interface 720 allowsa different AED enclosure to be selected.

In various embodiments, the apparatus 700 displays AED readiness statusdata 710 relating to the readiness of an AED registered to be disposedwithin the selected AED enclosure, such as, for example, informationrelated to an AED enclosure event that is classified as belonging to amaintenance event category. For example, in certain embodiments, the AEDreadiness status information includes data such as, for example, whetherthe AED battery has a charge level that satisfies one or morepredetermined criteria for voltage or storage capacity to ensure thatthe AED will operate correctly and an AED emergency response event. TheAED readiness status data 710 depicted also indicates whether the padexpiration date satisfies the predetermined criteria as to whether thepads are still within an acceptable range of dates prior to apredetermined expiration date.

The AED readiness status data 710 also includes, in certain embodiments,an indicator is whether a self-test performed by the AED passed orfailed as detected by a beep code interpreted by a stationary embodimentof the AED readiness apparatus 304 or as recorded through user input tothe user interface by a mobile embodiment of the AED readiness apparatus404. In various embodiments, the AED readiness status data 710 furtherindicates whether the AED registered to be disposed within the locationassociated with the selected AED enclosure identifier 706 is present andcorrectly disposed within the AED enclosure as detected by a stationaryembodiment of the AED readiness apparatus 104 such as depicted in FIG. 3or a mobile embodiment of the AED readiness apparatus 104 such asdepicted in FIG. 4.

Other AED readiness status data 710 depicted in one embodiment includesinformation about whether the cabinet or enclosure temperature is withinan acceptable range and/or whether the sensor battery charge level meetsthe predetermined criteria for voltage and/or charge to ensure that thesensor battery is charged enough to operate correctly. In certainembodiments, the AED readiness status data 710 includes when the AEDenclosure was last checked, either by a fixed embodiment and/or a mobileembodiment of the AED readiness apparatus 104. In certain embodiments,the apparatus 700 displays a map 712 showing the location of theselected AED enclosure.

The AED readiness apparatus 704 and/or any of the other AED readinessapparatuses 304, 404, 504, and 604, which communicate data for theapparatus 700 to display are configurable to display any relevant AEDreadiness status information and in certain embodiments, to displayindividual or aggregated data regarding the readiness status of variousresponders who have enrolled, subscribed, or otherwise opted in toreceive response actions from the AED readiness apparatus correspondingto the selected AED enclosure. For example, at a school, a healthservices manager may use the apparatuses 600, 700 to display responderreadiness data for multiple responders and/or individual respondersrespectively.

FIG. 8 is a schematic flow chart diagram illustrating one embodiment ofa method 800 for independent AED readiness determination for automatedexternal defibrillator deployment. In one embodiment, the method 800begins and includes obtaining 802 event data for an automated externaldefibrillator (“AED”) enclosure event, the AED enclosure eventcorresponding to an AED registered to be disposed within an AEDenclosure, classifying 804 the AED enclosure event into a predeterminedevent category, and communicating 806 a response action, in response tothe AED enclosure event. In various embodiments, all or a portion of thesteps of the method 800 are performed by an instance of the AEDreadiness apparatus 104 including the controller 202 and/or thecommunication interface 204 (e.g., as depicted and described above withrespect to the AED readiness apparatuses 304, 404, 504, 604, and 704illustrated respectively in FIGS. 3, 4, 5 6, and 7).

FIG. 9 is a schematic flow chart diagram illustrating another embodimentof a method 900 for independent AED readiness determination for AEDdeployment. In certain embodiments, the method 900 includes waking up902 to connect to the data network 106 to communication event data foran automated external defibrillator (“AED”) enclosure event, where theAED enclosure event corresponds to an AED registered to be disposedwithin an AED enclosure. As used herein, with regard to certain decisionsteps such as 904, 906, 940, 954, the terms “time out,” “timed out,” orsimilar terms refer to implementations in which whether one or more AEDreadiness apparatuses are able to connect to the data network is subjectto a timeout period. For example, if the AED readiness apparatus isunable to connect within a predetermined time at step 904 using theprimary credentials (e.g., 211 a), it may be referred to as a timed outAED readiness apparatus. In various embodiments, the AED readinessapparatus next attempts 906 to connect using the secondary credentials(e.g., 211 b) that may be pre-configured by an administrative interfaceto facilitate easy updating of a fleet of one or more AED readinessapparatuses without having to perform individual manual updates for eachAED readiness apparatus. For example, if a network password has beenupdated during a sleep period of one or more AED readiness apparatusesand secondary credentials have been provided via the administrativeinterface, then the method 900 connects to the network and moves thesecondary credentials to primary so that the on the next wake up 902,the AED readiness apparatus will try first to connect 904 with the newprimary credentials.

In response to determining that an AED readiness apparatus is currentlyunable to connect (e.g., timed out) after attempting to connect via theprimary credentials and the secondary credentials, a set of rescue steps938 through 956 may be taken as described in more detail below. Uponsuccessfully connecting to the data network, the method 900 continuesand communicates 910 AED enclosure event data for further processing ordisplay e.g., by a server, a dashboard, an application, and so forth.

In certain embodiments, the event data includes comparing 916 the userinput data 914 collected through a user interface and the sensor data912 collected through one or more sensors that are physically separatefrom the AED and electrically unconnected to the AED. In someembodiments, the method further includes comparing 916 the user inputdata 914 and the sensor data 912 and communicating 918 results of thecomparison to a mobile communication device and/or to a secondcommunication device. Such a comparison may beneficially assist indetermining whether the sensors are operating correctly and/or whetherusers are aware of and correctly monitoring AED readiness status.

In various embodiments, the method 900 includes classifying 920 the AEDenclosure event data into event categories. One example of an AEDemergency response event category is an emergency response event 922. Anemergency response event can indicate that the AED was removed from theenclosure in response to a medical emergency such as a cardiac arrest.Keeping track of emergency response events may beneficially alert thosewith responsibility for use and maintenance of the AED to follow up tosee whether any consumable supplies such as pads were used or whetherthe AED functioned as expected during the emergency response.

Another category of AED enclosure event is a maintenance event 924. Insome embodiments, tracking maintenance events 924 enables a user to knowand have a record of the dates and times that that maintenance of theAED has been performed.

In some embodiments, the method includes communicating 936 a responseaction to facilitate configuration of the AED enclosure with an updatedcontroller configured to collect the sensor data from at least one ofthe one or more sensors disposed within the AED enclosure. A thirdexample of an AED enclosure event category is a fault event 926. Incertain embodiments, a fault event 926 may indicate a fault in the AEDsuch as a sensor detecting a parameter such as temperature, humidity,battery voltage, and so forth, falling outside of expected operatingboundaries. In some embodiments, a fault event 926 may indicate a faultin the AED readiness apparatus such as a battery that has lower thanexpected charge, or a malfunctioning sensor. In various embodiments,sensing and communicating fault events can be utilized to improve AEDreadiness.

In certain embodiments, the method 900 further includes determining 928a responder readiness status such as, for example, a training status930, a responder location 932, and/or a readiness status indicated byuser input 934. Each of these status types may be used to promoteawareness and/or improve the training of current or potential futureresponders. The above examples are merely representative of numerousresponder readiness parameters that may be determined and/orcommunicated by the method 900.

The method 900 continues and, in various embodiments, includescommunicating 936 a response action for the detected AED enclosureevent. In some embodiments, communicating 936 the response action to themobile communication device is performed in response to determining thatthe mobile communication device corresponds to a responder having areadiness status that satisfies one or more predetermined criteria forthe predetermined event category. For example, the method maycommunicate a response action involving more detailed medical terms andactions in response to determining that the responder is a well-trainedemergency responder rather than a person with little or no recordedtraining in AED usage.

In various embodiments, after communicating 936 one or more responseactions for the detected AED enclosure event, the method 900 ends orsleeps 958 to reawaken periodically according to a predeterminedschedule.

Turning now to the rescue procedure which is depicted in actions 938through 956 of FIG. 9. In certain embodiments, in response todetermining that attempting 906 to connect the AED readiness apparatusto the data network is unsuccessful using either the primary or thesecondary credentials, the method 900 attempts 938 to connect to a datanetwork using a rescue procedure and rescue credentials. In suchembodiments, a first portion of the AED reading apparatus and/or therescue module may be implemented in a stationary electronic devicepositioned with the AED enclosure as depicted in FIG. 2, the rescuecredentials may be preconfigured in the code 208 (e.g., firmware for theAED readiness apparatus 104.

For example, the rescue module 218 may temporarily configure a mobilecommunication device 102 such as a tablet or smart phone as a networkaccess point, also referred to as a “hotspot.” For example, in certainembodiments, the mobile communication device 102 acts as a WiFi networkto which the AED readiness apparatus temporarily connects, in view ofthe fact that the AED readiness apparatus was unable to connect to thedesired data network 106 either because the primary credentials 211 aare no longer valid for that network because the network password waschanged to a new password without the secondary credentials 211 b havingbeen preconfigured with the new password, or because the access point109 to which a stationary implementation of an AED readiness apparatus104, 304, typically connects was out of service at the time of theconnection attempt.

In such embodiments, the rescue credentials 211 c are preconfigured infirmware in stationary embodiments of the AED readiness apparatus 104,304 and are similarly preconfigured in a rescue application that isaccessible online via the mobile communication device 102 that is actingas the hotspot. By connecting via the hotspot, the AED readinessapparatus can send 944 rescue data, such as updated primary credentialsand/or secondary credentials, and may take actions to facilitate networkconnections going forward. In certain embodiments, the AED readinessapparatus may send certain data such as AED enclosure event data whileconnected via the rescue credentials and/or may wait to send some AEDenclosure event data until the AED readiness apparatus has reestablishedconnection using updated primary credentials 211 a received as part ofthe rescue procedure.

In some embodiments, the method 900 flags 946 that the networkconnection was established via the rescue credentials and in response,receives 948 updated credentials for the data network. For example,updated primary credentials 211 a (depicted in FIGS. 2 and 6B) may beprovided to the rescue procedure e.g., through the administrativeinterface 602. The method 900 continues and the AED readiness apparatusdisconnects 950 from the network using the hotspot and rescuecredentials and attempts to connect 952 using the new primarycredentials. In response to being able to connect using the new primarycredentials provide as part of the rescue procedure, the method 900 maymove 956 the new credentials to the memory of the AED readinessapparatus as the primary credential 211 a.

In response to not being able to connect with the new primarycredentials provided while connected via the rescue credentials, aportion of the rescue process may alert 955 locally (e.g., by sounding aseries of beeps, flashing lights, or similar alert actions) that the AEDreadiness apparatus was unable to connect) after which the method 900may repeat, i.e., go back to action 938 of the method. Similarly, if themethod 900 is unable to connect via the rescue credentials. the AEDapparatus may time out, reset, and/or sleep/reawake (e.g., return tostep 902) if the AED readiness apparatus is unable to connect via therescue credentials (e.g., timed out at step 940). In some embodiments,the method 900 may provide an alert 942 (such as a series of audiblebeeps and/or visible flashes to attract the attention of a person at theplace of deployment of the AED readiness apparatus. The alert may signalthat the AED readiness apparatus may be due for service.

In various embodiments, all or a portion of the steps of the method 900are performed by an instance of the AED readiness apparatus 104including the controller 202 and/or the communication interface 204(e.g., as depicted and described above with respect to the AED readinessapparatuses 304, 404, 504, 604, and 704 illustrated respectively inFIGS. 3, 4, 5, 6, and 7).

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

What is claimed is:
 1. An apparatus comprising: a controller configuredto detect an automated external defibrillator (“AED”) enclosure eventcorresponding to an AED registered to be disposed within an AEDenclosure, wherein the controller is configured to communicate data forclassifying an AED enclosure event into a predetermined event category;and a communication interface configured to communicate a responseaction in response to data of the AED enclosure event satisfying one ormore predetermined criteria for the predetermined event category,wherein the communication interface is configured to periodically awakenand attempt to establish a wireless network connection for communicatingAED enclosure event data using one or more credentials of apredetermined series of credentials selected from primary credentials,secondary credentials, and rescue credentials.
 2. The apparatus of claim1, wherein the controller is configured to collect one or more AEDreadiness parameters selected from: an individual enclosure identifierfor linking the AED enclosure to an individual AED identifier of the AEDregistered to be disposed within the AED enclosure; an enclosure accessindicator that indicates whether the AED enclosure is open; anAED-presence indicator that indicates whether the AED is correctlydisposed within the AED enclosure; an audible readiness indicator of theAED; a visual readiness indicator of the AED; and a storage environmentindicator comprising one or more of temperature, humidity within the AEDenclosure.
 3. The apparatus of claim 2, wherein the controller isconfigured to collect the one or more AED readiness parameters using oneor more of: a sensor that is physically separate from and electricallyunconnected to the AED; and a user interface of a mobile communicationdevice.
 4. The apparatus of claim 3, wherein the individual enclosureidentifier is externally coupled to the AED enclosure, internally storedin a tangible memory, or a combination thereof.
 5. The apparatus ofclaim 3, wherein the sensor is disposed inside the AED enclosure.
 6. Theapparatus of claim 2, wherein the controller is configured tocommunicate with an access sensor configured to determine whether anaccess door of the AED enclosure is open.
 7. The apparatus of claim 6,wherein the apparatus is configured to wake the controller from adormant mode to an active mode in response to the access sensordetermining that the access door is open.
 8. The apparatus of claim 2,wherein the controller further communicates with an object sensorconfigured to determine whether the AED is disposed correctly within theAED enclosure.
 9. The apparatus of claim 8, wherein the object sensorcomprises a time-of-flight sensor configured to measure a reflectedsignal distance to determine whether the AED is disposed within the AEDenclosure.
 10. The apparatus of claim 2, wherein the controllercommunicates with an input transducer configured to collect audio dataof the audible readiness indicator.
 11. The apparatus of claim 10,further comprising a filter that distinguishes the audible readinessindicator from sounds that fail to satisfy predetermined parameters forthe audible readiness indicator.
 12. The apparatus of claim 11, whereinthe filter performs frequency domain processing and time domainprocessing on the audio data captured by the input transducer todistinguish the audible readiness indicator from the sounds that fail tosatisfy the predetermined parameters for the audible readinessindicator.
 13. The apparatus of claim 2, wherein the controllercomprises part of a communication device external to the AED enclosure,the communication device comprising a user interface configured tocollect the one or more AED readiness parameters through the userinterface.
 14. A method comprising: initiating a request for a networkconnection between a plurality of stationary AED readiness apparatusesand a data network using one or more credentials of a predeterminedseries of credentials selected from primary credentials, secondarycredentials, and rescue credentials for authenticating the plurality ofstationary AED readiness apparatuses to the data network; and inresponse to establishing the network connection between the plurality ofstationary AED readiness apparatuses and the data network: communicatingevent data for an automated external defibrillator (“AED”) enclosureevent, the AED enclosure event corresponding to an AED registered to bedisposed within an AED enclosure; classifying the AED enclosure eventinto a predetermined event category; and communicating a response actionin response to the AED enclosure event.
 15. The method of claim 14,wherein the event data comprises user input data collected through auser interface and sensor data collected through one or more sensorsthat are physically separate from the AED and electrically unconnectedto the AED, the method further comprising: performing a comparison ofthe user input data and the sensor data; and communicating results ofthe comparison to a mobile communication device, a second communicationdevice, or a combination thereof.
 16. The method of claim 15, whereinthe event data comprises user input data collected through a userinterface, the method further comprising communicating the responseaction to facilitate configuration of the AED enclosure with an updatedcontroller configured to collect the sensor data from at least one ofthe one or more sensors disposed within the AED enclosure.
 17. Themethod of claim 15, wherein the predetermined event category for the AEDenclosure event is selected from an emergency response event, amaintenance event, a fault event, and combinations thereof.
 18. Themethod of claim 17, wherein communicating the response action to themobile communication device is performed in response to determining thatthe mobile communication device corresponds to a responder having areadiness status that satisfies one or more predetermined criteria forthe predetermined event category.
 19. The method of claim 18, furthercomprising determining the readiness status of the responder based on aparameter selected from a level of training to respond to the AEDenclosure event, a location of the mobile communication devicecorresponding to the responder, a user input indicating the readinessstatus of the responder, an AED event response history of the responder,and combinations thereof.
 20. A computer program product comprising anon-transitory computer readable storage medium having programinstructions embodied therewith, wherein the program instructions areexecutable by a mobile communication device to cause the mobilecommunication device to: configure a predetermined series of credentialsselected from primary credentials and secondary credentials forattempting to connect a plurality of stationary AED readinessapparatuses to a data network; configure a mobile communication deviceas a temporary access point accessible using predetermined rescuecredentials for one or more timed out AED readiness apparatuses tocommunicate one or more updated primary credentials and/or secondarycredentials to the timed out AED readiness apparatuses; and in responseto the AED readiness apparatuses connecting to the data network: obtainevent data for an automated external defibrillator (“AED”) enclosureevent detected by a detector controller, the AED enclosure eventcorresponding to an AED registered to be disposed within an AEDenclosure; obtain responder data indicating a readiness status for aresponder that is a user of the mobile communication device; andcommunicate a response action in response to classifying the AEDenclosure event into a predetermined event category and determining thatthe readiness status for the responder satisfies predetermined criteria.